-
Notifications
You must be signed in to change notification settings - Fork 8.2k
driver: clock_control: renesas_ra: Defining MSTP regs in devicetree #76820
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
d5a828b to
68ae8f0
Compare
duynguyenxa
previously approved these changes
Aug 19, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@soburi , Seem good to me, we've checked this on RA8M1 hardware
476c71d to
08dfdd2
Compare
08dfdd2 to
14e9e19
Compare
KhiemNguyenT
previously approved these changes
Aug 21, 2024
Allows MSTP register addresses to be changed in the device tree to support different configuration SoCs. Signed-off-by: TOKITA Hiroshi <[email protected]>
When omitting the clk_src definition in a child node of a pclkblock, it uses the source of the parent node. Signed-off-by: TOKITA Hiroshi <[email protected]>
14e9e19 to
b171bf1
Compare
KhiemNguyenT
approved these changes
Aug 22, 2024
duynguyenxa
approved these changes
Aug 28, 2024
soburi
added a commit
to soburi/zephyr
that referenced
this pull request
Aug 28, 2024
Add a definition for RA4, which was not included in zephyrproject-rtos#76820. Signed-off-by: TOKITA Hiroshi <[email protected]>
nashif
pushed a commit
that referenced
this pull request
Aug 28, 2024
Add a definition for RA4, which was not included in #76820. Signed-off-by: TOKITA Hiroshi <[email protected]>
Chenhongren
pushed a commit
to Chenhongren/zephyr
that referenced
this pull request
Sep 6, 2024
Add a definition for RA4, which was not included in zephyrproject-rtos#76820. (cherry picked from commit 1ffd746) Original-Signed-off-by: TOKITA Hiroshi <[email protected]> GitOrigin-RevId: 1ffd746 Cr-Build-Id: 8738238973287044049 Cr-Build-Url: https://cr-buildbucket.appspot.com/build/8738238973287044049 Copybot-Job-Name: zephyr-main-copybot-downstream Change-Id: Idd2bc8bc5cb47ce9da5105edbd65f1bd4473b378 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/zephyr/+/5827586 Tested-by: ChromeOS Prod (Robot) <[email protected]> Tested-by: Ting Shen <[email protected]> Reviewed-by: Ting Shen <[email protected]> Commit-Queue: Ting Shen <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area: Clock Control
area: Devicetree Binding
PR modifies or adds a Device Tree binding
platform: Renesas RA
Renesas Electronics Corporation, RA
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Allows MSTP register addresses to be changed in the device tree
to support different configuration SoCs.
When omitting the clk_src definition in a child node of a pclkblock,
it uses the source of the parent node.
The impact is still limited, so we are currently correcting the names.Since I don't have an RA8M1 environment, I verified this PR with RA4M1 only.